Author: Halfvares Mats, Teknikhuset AB.

Published: 2004-11-22

Applies to:
  • Content Studio ver. 4.0 build 1006

Type: Information

Symptoms

After upgrading to Content Studio ver. 4.0 build 1006 or later users might see the message "Permission denied" after entering the Content Studio administrative interface.

Cause

This might be the result of improved security in Content Studio. In order to list objects within a container the caller must have the READ/LIST permission to see anything even though the user has permission to underlying objects. This will be more like the behaviour in the file system.

Resolution

An administrator should set permission for the users / groups that should be able to list content and this permission must be set on the root and further down. Setting an ordinary READ/LIST permission will however grant the user this permission on all objects below this point. To solve this dilemma the administrator can open the advanced security dialog, select the trustee in question and click the properties for access control entry dialog. In the drop down apply this permission to this folder only. This will prevent the permission to inherit further down on the tree. The same goes for the units and categories as well. Th give all users the desired access you should consider using the NT AUTHORITY\Authenticated Users group rather that Everyone or BUILTIN\Users.

Status

This behaviour is by design and is implemented to be more in consequences with the underlying file system.

More information

It can be rather difficult to implement the behaviour that users only should see what they have access to. You might find it better to use the Simple mode instead or implement editing on the website instead.